Display Management for Native User Experiences

ABSTRACT

In some remote application execution environments, a client device (e.g., to which application output is sent and where user interaction is performed) may include native control elements for touch input such as virtual keyboards, virtual pickers and the like. When the server device detects an editable/control field of a remoted application receiving focus, the server may instruct the client to activate a native control element for user interaction. The client may determine the manner in which to modify an application display to resolve potential display conflicts. For example, a native control element may obscure or hide portions of the remoted application on the client display. Modifying the application display may include panning the display, zooming into or out of portions of the display, adapting the display for scrolling, and the like. The remote computing device may also transmit values for populating a native control element.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.13/253,414, entitled “DISPLAY MANAGEMENT FOR NATIVE USER EXPERIENCES,”filed on Oct. 5, 2011, which claims the benefit of priority from U.S.Provisional Application No. 61/389,975, entitled “NATIVE USER EXPERIENCEFOR REMOTE APPLICATIONS DISPLAYED ON MOBILE DEVICES,” filed on Oct. 5,2010. The contents of the above applications are hereby incorporated byreference in their entirety.

TECHNICAL FIELD

Aspects described herein generally relate to displaying remotelyexecuting applications on devices. For example, aspects relate toproviding a native application interaction experience on a device.

BACKGROUND

Devices, including stationary devices such as personal computers andworkstations and mobile devices such as smart phones and tabletcomputers, may execute operating systems and applications that aretouch-friendly (e.g., compatible with touch input). These operatingsystems and applications often allow users to interact with menus andapplications designed to accommodate using a touch screen as an inputdevice. For example, some applications may be designed to handle a touchscreen as the primary input such that when an editable control or fieldis selected or receives focus, the event may cause a virtual keyboard toappear. FIG. 4A illustrates an example native mobile device applicationthat permits a user to enter information into an editable field via avirtual keyboard displayed on the screen, and permits a user to selectfrom a drop down box (e.g., combo box) using a virtual selector orpicker control. In each of these examples, the touch screen of themobile device may be used as the input device.

In some instances, an application may be displayed on a device that isnot formatted for touch-screen input. For example, in some cases anapplication remotely executing on a server may be remotely displayed ona device as shown in FIG. 4B. In FIG. 4B, a virtual keyboard isdisplayed over the editable control or field such that the user mightnot be able to see the control while the user is trying to input datainto the control, thus making user input difficult. Additionally, theuser may be required to manually activate the native control element ofthe client device, instead of being provided a native control elementthat is automatically triggered in response to selection of an editablearea. Other input and viewability issues might also arise from touchcompatible input elements being displayed on a remote device.

BRIEF SUMMARY

The following presents a simplified summary of the disclosure in orderto provide a basic understanding of some aspects. It is not intended toidentify key or critical elements of the disclosure or to delineate thescope of the disclosure. The following summary merely presents someconcepts of the disclosure in a simplified form as a prelude to the moredetailed description provided below.

According to one or more aspects, a display of a remoted application andnative control elements may be managed so that one or more portions ofthe remoted application display are not obscured or hidden by activenative control elements. In one example, a remote computing deviceexecuting the application for a client device may receive a notificationwhen the application or a control element within the applicationreceives focus. Upon receiving the notification, the remote computingdevice may notify the client device to modify the display of theapplication as necessary (e.g., to reflect the focus) and/or todetermine a type of control element corresponding to the control elementwithin the remoted application receiving focus. Additionally oralternatively, the remote computing device may instruct the clientdevice to activate a native control element corresponding to thedetermined type of control element. The client device may then identifya native control element matching the determined type or category ofcontrol element and active the native control element. In somearrangements, the client device may further determine whether the nativecontrol element will overlap or otherwise obscure one or more portionsof the remoted application display when activated. If so, the clientdevice may modify the local display to avoid obscuring the remotedapplication display or the area of focus. Modification of theapplication display may include panning, zooming, scrolling and thelike.

According to another aspect, the client device may transmit confirmationand update messages to the remote computing device. The confirmation andupdate messages may include status information for the native controlelement and notifications of user interaction with the native controlelement.

In some arrangements, the remote computing device executing theapplication may determine whether the native control element willobscure the application display and determine a manner in which tomodify the local display of the client device.

According to another aspect, a remote computing device executing theapplication may transmit values of an application control elementreceiving focus to the client device for populating the native controlelement. In one example, if the application control element receivingfocus is a drop down menu, the values within the drop down menu may betransmitted to the client device for display in a native picker controlelement of the client device.

According to yet another aspect, if a client device does not have nativecontrol elements, the remote computing device may generate a virtualcontrol element and remote the control element to the client devicesimilar to remoting an application to which input or interaction is tobe registered. For example, if the client device is not capable ofshowing a local software keyboard, then an in-session keyboard (e.g.,remoted by the server) may be displayed instead. The display of thein-session keyboard may be remoted (e.g., graphics transmitted) to theclient device for use thereon.

The details of these and other embodiments of the present disclosure areset forth in the accompanying drawings and the description below. Otherfeatures and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1A illustrates an example network environment that may beconfigured to provide remote access to computing devices and applicationprograms executing thereon according to one or more aspects describedherein.

FIG. 1B and FIG. 1C are block diagrams illustrating example computingdevices according to one or more aspects described herein.

FIG. 2A is a block diagram illustrating an example system for displayinga plurality of resources in a user-configurable display layout on anexternal display device according to one or more aspects describedherein.

FIG. 2B is a block diagram illustrating an example system for mapping adisplay of one or more resources to one or more display devicesaccording to one or more aspects described herein.

FIG. 2C illustrates an example interface displaying a plurality ofresources in a user-configurable display layout on an external displaydevice, the user-configurable display layout divided into a gridaccording to one or more aspects described herein.

FIG. 2D illustrates an example interface displaying a plurality ofresources in a user-configurable, dynamic display layout on an externaldisplay device according to one or more aspects described herein.

FIG. 3A is a block diagram illustrating example screen spaces providedby a mobile computing device attached to one or more external displaydevices according to one or more aspects described herein.

FIG. 3B is a block diagram illustrating an example mobile computingdevice providing a plurality of screen spaces according to one or moreaspects described herein.

FIG. 3C is a block diagram illustrating an example logicalrepresentation of a plurality of screen spaces managed by a virtualgraphics driver according to one or more aspects described herein.

FIG. 4A is an example known interface displaying an applicationexecuting locally on a mobile device.

FIG. 4B is an example known interface displaying a remoted applicationon a mobile device.

FIG. 4C illustrates an example interface displaying a remotedapplication on a mobile device according to one or more aspectsdescribed herein.

FIG. 5 is a block diagram illustrating an example system for alteringthe display of a remoted application on a mobile device according to oneor more aspects described herein.

FIG. 6 is a flow diagram illustrating an example method for altering thedisplay of a remoted application on a mobile device according to one ormore aspects described herein.

FIG. 7 is a flowchart illustrating a method for modifying a remotedapplication display to accommodate the activation of native controlelements according to one or more aspects described herein.

FIG. 8 is a flowchart illustrating a method for managing a display on adevice based on the activation of native control elements according toone or more aspects described herein.

FIG. 9A and FIG. 9B illustrate an example sequence of user interfaces inwhich a native input element is activated and a display of anapplication is modified according to one or more aspects describedherein.

FIG. 10A and FIG. 10B illustrate another example sequence of userinterfaces in which a native input element is activated and a display ofan application is modified according to one or more aspects describedherein.

DETAILED DESCRIPTION

Applications may be executed remotely by a first computing device foruse at a second computing device (e.g., a client device). By using aremoted application, the client device may use processing power by thefirst computing device to execute the functionality and features of theremoted application. Additionally, data and applications may be servedat a location that is accessible from multiple remote locations (e.g.,through a public and/or private network).

FIG. 1A illustrates an example computing environment 101 that includesone or more client machines 102A-102N (collectively referred to hereinas “client machine(s) 102”) that are in communication with one or moreservers 106A-106N (generally referred to herein as “server(s) 106”).Installed in between the client machine(s) 102 and server(s) 106 is anetwork.

In one example, the computing environment 101 can include an appliance(e.g., a device or apparatus) installed between the server(s) 106 andclient machine(s) 102. This appliance can manage client/serverconnections, and in some cases can load balance client connectionsamongst a plurality of backend servers.

The client machine(s) 102 may, in some examples, be a single clientmachine 102 or a single group of client machines 102, while server(s)106 may be a single server 106 or a single group of servers 106. In oneexample, a single client machine 102 may communicate with more than oneserver 106, while in another example, a single server 106 maycommunicate with more than one client machine 102. In yet anotherexample, a single client machine 102 might only communicate with asingle server 106.

A client machine 102 may, in some examples, be referenced by any one ofthe following terms: client machine(s) 102; client(s); clientcomputer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); endpoint node(s);or a second machine. The server 106, in some examples, may be referencedby any one of the following terms: server(s), local machine; remotemachine; server farm(s), host computing device(s), or a firstmachine(s).

According to one or more arrangements, the client machine 102 may be avirtual machine 102C. The virtual machine 102C may be any virtualmachine, while in some configurations, the virtual machine 102C may beany virtual machine managed by a hypervisor developed by XenSolutions,Citrix Systems, IBM, VMware, or any other hypervisor. In other examples,the virtual machine 102C can be managed by any hypervisor, while instill other examples, the virtual machine 102C can be managed by ahypervisor executing on a server 106 or a hypervisor executing on aclient 102.

The client machine 102 may, in some examples, execute, operate orotherwise provide an application such as: software; a program;executable instructions; a virtual machine; a hypervisor; a web browser;a web-based client; a client-server application; a thin-client computingclient; an ActiveX control; a Java applet; software related to voiceover internet protocol (VoIP) communications like a soft IP telephone;an application for streaming video and/or audio; an application forfacilitating real-time-data communications; a HTTP client; a FTP client;an Oscar client; a Telnet client; or any other set of executableinstructions. Accordingly, in at least some arrangements, remoting anapplication may include a client device 102 receiving and displayingapplication output generated by an application remotely executing on aserver 106 or other remotely located machine or computing device. Forexample, the client device 102 may display the application output in anapplication window, a browser, or other output window. In one example,the application is a desktop, while in other examples the application isan application that generates a desktop. A desktop may include agraphical shell providing a user interface for an instance of anoperating system in which local and/or remote applications can beintegrated. Applications, as used herein, are programs that executeafter an instance of an operating system (and, optionally, also thedesktop) has been loaded. Each instance of the operating system may bephysical (e.g., one operating system per device) or virtual (e.g., manyinstances of an OS running on a single device). Each application may beexecuted on a local device, or executed on a remotely located device(e.g., remoted). Applications may be remoted in multiple ways. In oneexample, applications may be remoted in a seamless manner in whichwindows are created on the client device so as to make the applicationdisplay seem as if it were running locally on the client device and thedesktop thereof. In another example, a remoted application may beprovided in a windowed mode where a desktop is remoted to the clientdevice and the application is displayed as an application executing inthe remoted desktop. Various other remoting methods and techniques mayalso be implemented or used.

According to some aspects, the server 106 may execute a remotepresentation client or other client or program that uses a thin-clientor remote-display protocol to capture display output generated by anapplication executing on a server 106 and to subsequently transmit theapplication display output to a remote client 102. The thin-client orremote-display protocol can be any one of the following protocols (orother suitable protocol): the Independent Computing Architecture (ICA)protocol manufactured by Citrix Systems, Inc. of Ft. Lauderdale, Fla.;or the Remote Desktop Protocol (RDP) manufactured by the MicrosoftCorporation of Redmond, Wash.

The computing environment can include more than one server 106A-106Nsuch that the servers 106A-106N are logically and/or physically groupedtogether into a server farm 106. In one example, the server farm 106 caninclude servers 106 that are geographically dispersed and logicallygrouped together in a server farm 106, or, in another example, servers106 that are located proximate to each other and logically groupedtogether in a server farm 106. Geographically dispersed servers106A-106N within a server farm 106 can, in some examples, communicateusing a WAN, MAN, or LAN, where different geographic regions can becharacterized as: different continents; different regions of acontinent; different countries; different states; different cities;different zip codes; different neighborhoods; different campuses;different rooms; or any combination of the preceding geographicallocations. In some examples, the server farm 106 may be administered asa single entity, while in other examples, the server farm 106 caninclude multiple server farms 106.

A server farm 106 may include servers 106 that execute a substantiallysimilar type of operating system platform (e.g., WINDOWS NT,manufactured by Microsoft Corp. of Redmond, Wash., UNIX, LINUX, or SNOWLEOPARD.) In other examples, the server farm 106 can include a firstgroup of servers 106 that execute a first type of operating systemplatform, and a second group of servers 106 that execute a second typeof operating system platform. The server farm 106, in other examples,can include servers 106 that execute different types of operating systemplatforms.

The server 106, in some examples, may be of any server type. In otherexamples, the server 106 can be any of the following server types: afile server; an application server; a web server; a proxy server; anappliance; a network appliance; a gateway; an application gateway; agateway server; a virtualization server; a deployment server; a SSL VPNserver; a firewall; a web server; an application server or as a masterapplication server; a server 106 executing an active directory; or aserver 106 executing an application acceleration program that providesfirewall functionality, application functionality, or load balancingfunctionality. In some examples, a server 106 may be a RADIUS serverthat includes a remote authentication dial-in user service. Inarrangements where the server 106 includes an appliance, the server 106may be an appliance manufactured by any one of the followingmanufacturers: the Citrix Application Networking Group; Silver PeakSystems, Inc; Riverbed Technology, Inc.; F5 Networks, Inc.; or JuniperNetworks, Inc. Some examples include a first server 106A that receivesrequests from a client machine 102, forwards the request to a secondserver 106B, and responds to the request generated by the client machine102 with a response from the second server 106B. The first server 106Amay acquire an enumeration of applications available to the clientmachine 102 as well as address information associated with anapplication server 106 hosting an application identified within theenumeration of applications. The first server 106A may then present aresponse to the client's request using a web interface, and communicatedirectly with the client 102 to provide the client 102 with access to anidentified application.

The server 106 may, in some examples, execute any one of the followingapplications: a thin-client application using a thin-client protocol totransmit application display data to a client; a remote displaypresentation application; any portion of the CITRIX ACCESS SUITE byCitrix Systems, Inc. like the METAFRAME, CITRIX PRESENTATION SERVER,CITRIX XENAPP or CITRIX XENDESKTOP server; MICROSOFT WINDOWS TerminalServices manufactured by the Microsoft Corporation; or an ICA client,developed by Citrix Systems, Inc. Another example includes a server 106that is an application server such as: an email server that providesemail services such as MICROSOFT EXCHANGE manufactured by the MicrosoftCorporation; a web or Internet server; a desktop sharing server; acollaboration server; or any other type of application server. Stillother examples include a server 106 that executes any one of thefollowing types of hosted servers applications: GOTOMEETING provided byCitrix Online Division, Inc.; WEBEX provided by WebEx, Inc. of SantaClara, Calif.; or Microsoft Office LIVE MEETING provided by MicrosoftCorporation.

Client machines 102 may, in some examples, be a client node that seeksaccess to resources provided by a server 106. In other examples, theserver 106 may provide clients 102 or client nodes with access to hostedresources. The server 106, in some examples, functions as a master nodesuch that it communicates with one or more clients 102 or servers 106.In some examples, the master node may identify and provide addressinformation associated with a server 106 hosting a requestedapplication, to one or more clients 102 or servers 106. In still otherexamples, the master node may be a server farm 106, a client 102, acluster of client nodes 102, or an appliance.

One or more clients 102 and/or one or more servers 106 may transmit dataover a network 104 installed between machines and appliances within thecomputing environment 101. The network 104 may comprise one or moresub-networks, and may be installed between any combination of theclients 102, servers 106, computing machines and appliances includedwithin the computing environment 101. In some examples, the network 104may be: a local-area network (LAN); a metropolitan area network (MAN); awide area network (WAN); a primary network 104 comprised of multiplesub-networks 104 located between the client machines 102 and the servers106; a primary public network 104 with a private sub-network 104; aprimary private network 104 with a public sub-network 104; or a primaryprivate network 104 with a private sub-network 104. Still furtherexamples include a network 104 that may be any of the following networktypes: a point to point network; a broadcast network; atelecommunications network; a data communication network; a computernetwork; an ATM (Asynchronous Transfer Mode) network; a SONET(Synchronous Optical Network) network; a SDH (Synchronous DigitalHierarchy) network; a wireless network; a wireline network; or a network104 that includes a wireless link where the wireless link may be aninfrared channel or satellite band. The network topology of the network104 may differ within different examples, possible network topologiesinclude: a bus network topology; a star network topology; a ring networktopology; a repeater-based network topology; or a tiered-star networktopology. Additional examples may include a network 104 of mobiletelephone networks that use a protocol to communicate among mobiledevices, where the protocol may be any one of the following: AMPS; TDMA;CDMA; GSM; GPRS UMTS; or any other protocol able to transmit data amongmobile devices.

FIG. 1B illustrates an example computing device 100. The client machine102 and server 106 illustrated in FIG. 1A may be deployed as and/orexecuted on any example of computing device 100 illustrated anddescribed herein or any other computing device. Included within thecomputing device 100 is a system bus 150 that communicates with thefollowing components: a central processing unit 121; a main memory 122;storage memory 128; an input/output (I/O) controller 123; displaydevices 124A-124N; an installation device 116; and a network interface118. In one example, the storage memory 128 includes: an operatingsystem, software routines, and a client agent 120. The I/O controller123, in some examples, is further connected to a key board 126, and apointing device 127. Other examples may include an I/O controller 123connected to one or more of input/output devices 130A-130N.

FIG. 1C illustrates an example computing device 100, where the clientmachine 102 and server 106 illustrated in FIG. 1A may be deployed asand/or executed on any example of the computing device 100 illustratedand described herein or any other computing device. Included within thecomputing device 100 is a system bus 150 that communicates with thefollowing components: a bridge 170, and a first I/O device 130A. Inanother example, the bridge 170 is in further communication with themain central processing unit 121, where the central processing unit 121may further communicate with a second I/O device 130B, a main memory122, and a cache memory 140. Included within the central processing unit121, are I/O ports, a memory port 103, and a main processor.

Examples of the computing machine 100 may include a central processingunit 121 characterized by any one of the following componentconfigurations: logic circuits that respond to and process instructionsfetched from the main memory unit 122; a microprocessor unit, such as:those manufactured by Intel Corporation; those manufactured by MotorolaCorporation; those manufactured by Transmeta Corporation of Santa Clara,Calif.; the RS/6000 processor such as those manufactured byInternational Business Machines; a processor such as those manufacturedby Advanced Micro Devices; or any other combination of logic circuits.Still other examples of the central processing unit 122 may include anycombination of the following: a microprocessor, a microcontroller, acentral processing unit with a single processing core, a centralprocessing unit with two processing cores, or a central processing unitwith more than one processing core.

While FIG. 1C illustrates a computing device 100 that includes a singlecentral processing unit 121, in some examples the computing device 100may include one or more processing units 121. In these examples, thecomputing device 100 may store and execute firmware or other executableinstructions that, when executed, direct the one or more processingunits 121 to simultaneously execute instructions or to simultaneouslyexecute instructions on a single piece of data. In other examples, thecomputing device 100 may store and execute firmware or other executableinstructions that, when executed, direct the one or more processingunits to each execute a section of a group of instructions. For example,each processing unit 121 may be instructed to execute a portion of aprogram or a particular module within a program.

In some examples, the processing unit 121 may include one or moreprocessing cores. For example, the processing unit 121 may have twocores, four cores, eight cores, etc. In one example, the processing unit121 may comprise one or more parallel processing cores. The processingcores of the processing unit 121, may in some examples access availablememory as a global address space, or in other examples, memory withinthe computing device 100 may be segmented and assigned to a particularcore within the processing unit 121. In one example, the one or moreprocessing cores or processors in the computing device 100 may eachaccess local memory. In still another example, memory within thecomputing device 100 may be shared amongst one or more processors orprocessing cores, while other memory may be accessed by particularprocessors or subsets of processors. In examples where the computingdevice 100 includes more than one processing unit, the multipleprocessing units may be included in a single integrated circuit (IC).These multiple processors, in some examples, may be linked together byan internal high speed bus, which may be referred to as an elementinterconnect bus.

In examples where the computing device 100 includes one or moreprocessing units 121, or a processing unit 121 including one or moreprocessing cores, the processors may execute a single instructionsimultaneously on multiple pieces of data (SIMD), or in other examplesmay execute multiple instructions simultaneously on multiple pieces ofdata (MIMD). In some examples, the computing device 100 may include anynumber of SIMD and MIMD processors.

The computing device 100, in some examples, may include a graphicsprocessor or a graphics processing unit (Not Shown). The graphicsprocessing unit may include any combination of software and hardware,and may further input graphics data and graphics instructions, render agraphic from the inputted data and instructions, and output the renderedgraphic. In some examples, the graphics processing unit may be includedwithin the processing unit 121. In other examples, the computing device100 may include one or more processing units 121, where at least oneprocessing unit 121 is dedicated to processing and rendering graphics.

In one example, computing machine 100 may include a central processingunit 121 that communicates with cache memory 140 via a secondary busalso known as a backside bus, while another example of the computingmachine 100 includes a central processing unit 121 that communicateswith cache memory via the system bus 150. The local system bus 150 may,in some examples, also be used by the central processing unit tocommunicate with more than one type of I/O device 130A-130N. In someexamples, the local system bus 150 may be any one of the following typesof buses: a VESA VL bus; an ISA bus; an EISA bus; a MicroChannelArchitecture (MCA) bus; a PCI bus; a PCI-X bus; a PCI-Express bus; or aNuBus. Alternatively or additionally, computing machine 100 may includean I/O device 130A-130N that is a video display 124 that communicateswith the central processing unit 121. Still other versions of thecomputing machine 100 include a processor 121 connected to an I/O device130A-130N via any one of the following connections: HyperTransport,Rapid I/O, or InfiniBand. Further examples of the computing machine 100include a processor 121 that communicates with one I/O device 130A usinga local interconnect bus and a second I/O device 130B using a directconnection.

The computing device 100, in some examples, includes a main memory unit122 and cache memory 140. The cache memory 140 may be any memory type,and in some examples may be any one of the following types of memory:SRAM; BSRAM; or EDRAM. Other examples include cache memory 140 and amain memory unit 122 that may be any one of the following types ofmemory: Static random access memory (SRAM), Burst SRAM or SynchBurstSRAM (BSRAM); Dynamic random access memory (DRAM); Fast Page Mode DRAM(FPM DRAM); Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM);Extended Data Output DRAM (EDO DRAM); Burst Extended Data Output DRAM(BEDO DRAM); Enhanced DRAM (EDRAM); synchronous DRAM (SDRAM); JEDECSRAM; PC100 SDRAM; Double Data Rate SDRAM (DDR SDRAM); Enhanced SDRAM(ESDRAM); SyncLink DRAM (SLDRAM); Direct Rambus DRAM (DRDRAM);Ferroelectric RAM (FRAM); or any other type of memory. Further examplesinclude a central processing unit 121 that may access the main memory122 via: a system bus 150; a memory port 103; or any other connection,bus or port that allows the processor 121 to access memory 122.

In one or more arrangements, computing device 100 may provide supportfor any one of the following installation devices 116: a CD-ROM drive, aCD-R/RW drive, a DVD-ROM drive, tape drives of various formats, USBdevice, a bootable medium, a bootable CD, a bootable CD for GNU/Linuxdistribution such as KNOPPIX®, a hard-drive or any other device suitablefor installing applications or software. Applications may, in someexamples, include a client agent 120, or any portion of a client agent120. The computing device 100 may further include a storage device 128that may be either one or more hard disk drives, or one or moreredundant arrays of independent disks; where the storage device isconfigured to store an operating system, software, programsapplications, or at least a portion of the client agent 120. Computingdevice 100 may also include an installation device 116 that is used asthe storage device 128.

The computing device 100 may further include a network interface 118 tointerface to a Local Area Network (LAN), Wide Area Network (WAN) or theInternet through a variety of connections including, but not limited to,standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56kb,X.25, SNA, DECNET), broadband connections (e.g., ISDN, Frame Relay, ATM,Gigabit Ethernet, Ethernet-over-SONET), wireless connections, or somecombination of any or all of the above. Connections may also beestablished using a variety of communication protocols (e.g., TCP/IP,IPX, SPX, NetBIOS, Ethernet, ARCNET, SONET, SDH, Fiber Distributed DataInterface (FDDI), RS232, RS485, IEEE 802.11, IEEE 802.11a, IEEE 802.11b,IEEE 802.11g, CDMA, GSM, WiMax and direct asynchronous connections). Oneversion of the computing device 100 includes a network interface 118able to communicate with additional computing devices 100′ via any typeand/or form of gateway or tunneling protocol such as Secure Socket Layer(SSL) or Transport Layer Security (TLS), or the Citrix Gateway Protocolmanufactured by Citrix Systems, Inc. Versions of the network interface118 may comprise any one of: a built-in network adapter; a networkinterface card; a PCMCIA network card; a card bus network adapter; awireless network adapter; a USB network adapter; a modem; or any otherdevice suitable for interfacing the computing device 100 to a networkcapable of communicating and performing the methods and systemsdescribed herein.

According to one or more aspects, computing device 100 may include anyone of the following I/O devices 130A-130N: a keyboard 126; a pointingdevice 127; mice; trackpads; an optical pen; trackballs; microphones;drawing tablets; video displays; speakers; inkjet printers; laserprinters; and dye-sublimation printers; or any other input/output deviceable to perform the methods and systems described herein. An I/Ocontroller 123 may in some examples connect to multiple I/O devices103A-130N to control the one or more I/O devices. In some examples, I/Odevices 130A-130N may be configured to provide storage or aninstallation medium 116, while others may provide a universal serial bus(USB) interface for receiving USB storage devices such as the USB FlashDrive line of devices manufactured by Twintech Industry, Inc.Additionally or alternatively, computing device 100 may include I/Odevice 130 that may be a bridge between the system bus 150 and anexternal communication bus, such as: a USB bus; an Apple Desktop Bus; anRS-232 serial connection; a SCSI bus; a FireWire bus; a FireWire 800bus; an Ethernet bus; an AppleTalk bus; a Gigabit Ethernet bus; anAsynchronous Transfer Mode bus; a HIPPI bus; a Super HIPPI bus; aSerialPlus bus; a SCI/LAMP bus; a FibreChannel bus; or a Serial Attachedsmall computer system interface bus.

In some examples, the computing machine 100 may connect to multipledisplay devices 124A-124N, in other examples the computing device 100may connect to a single display device 124, while in still otherexamples the computing device 100 connects to display devices 124A-124Nthat are the same type or form of display, or to display devices thatare different types or forms. Examples of the display devices 124A-124Nmay be supported and enabled by the following: one or multiple I/Odevices 130A-130N; the I/O controller 123; a combination of I/Odevice(s) 130A-130N and the I/O controller 123; any combination ofhardware and software able to support a display device 124A-124N; anytype and/or form of video adapter, video card, driver, and/or library tointerface, communicate, connect or otherwise use the display devices124A-124N. The computing device 100 may in some examples be configuredto use one or multiple display devices 124A-124N, these configurationsinclude: having multiple connectors to interface to multiple displaydevices 124A-124N; having multiple video adapters, with each videoadapter connected to one or more of the display devices 124A-124N;having an operating system configured to support multiple displays124A-124N; using circuits and software included within the computingdevice 100 to connect to and use multiple display devices 124A-124N; andexecuting software on the main computing device 100 and multiplesecondary computing devices to enable the main computing device 100 touse a secondary computing device's display as a display device 124A-124Nfor the main computing device 100. Still other examples of the computingdevice 100 may include multiple display devices 124A-124N provided bymultiple secondary computing devices and connected to the main computingdevice 100 via a network.

According to one or more arrangements, the computing machine 100 mayexecute any operating system including: versions of the MICROSOFTWINDOWS operating systems such as WINDOWS 3.x; WINDOWS 95; WINDOWS 98;WINDOWS 2000; WINDOWS NT 3.51; WINDOWS NT 4.0; WINDOWS CE; WINDOWS XP;and WINDOWS VISTA; the different releases of the Unix and Linuxoperating systems; any version of the MAC OS manufactured by AppleComputer; OS/2, manufactured by International Business Machines; anyembedded operating system; any real-time operating system; any opensource operating system; any proprietary operating system; any operatingsystems for mobile computing devices; or any other operating system. Insome examples, the computing machine 100 may execute multiple operatingsystems. For example, the computing machine 100 may execute PARALLELS oranother virtualization platform that may execute or manage a virtualmachine executing a first operating system, while the computing machine100 executes a second operating system different from the firstoperating system.

The computing machine 100 may be embodied in any one of the followingcomputing devices: a computing workstation; a desktop computer; a laptopor notebook computer; a server; a handheld computer (e.g., a tabletcomputer such as the iPad and iPad 2 manufactured by Apple Computer); amobile telephone; a portable telecommunication device; a media playingdevice; a gaming system; a mobile computing device; a netbook; a deviceof the IPOD family of devices manufactured by Apple Computer; any one ofthe PLAYSTATION family of devices manufactured by the Sony Corporation;any one of the Nintendo family of devices manufactured by Nintendo Co;any one of the XBOX family of devices manufactured by the MicrosoftCorporation; or any other type and/or form of computing,telecommunications or media device that is capable of communication andthat has sufficient processor power and memory capacity to perform themethods and systems described herein. In other examples the computingmachine 100 may be a mobile device such as any one of the followingmobile devices: a JAVA-enabled cellular telephone or personal digitalassistant (PDA), such as the i55sr, i58sr, i85s, i88s, i90c, i95c1, orthe im1100, all of which are manufactured by Motorola Corp; the 6035 orthe 7135, manufactured by Kyocera; the i300 or i330, manufactured bySamsung Electronics Co., Ltd; the TREO 180, 270, 600, 650, 680, 700p,700w, or 750 smart phone manufactured by Palm, Inc; any computing devicethat has different processors, operating systems, and input devicesconsistent with the device; or any other mobile computing device capableof performing the methods and systems described herein. In still otherexamples, the computing device 100 may be any one of the followingmobile computing devices: any one series of Blackberry, or otherhandheld device manufactured by Research In Motion Limited; the iPhonemanufactured by Apple Computer; Palm Pre; a Pocket PC; a Pocket PCPhone; or any other handheld mobile device.

In some examples, the computing device 100 may have differentprocessors, operating systems, and input devices consistent with thedevice. For example, in one example, the computing device 100 is a TREO180, 270, 600, 650, 680, 700p, 700w, or 750 smart phone manufactured byPalm, Inc. In some of these examples, the TREO smart phone is operatedunder the control of the PalmOS operating system and includes a stylusinput device as well as a five-way navigator device.

According to one or more configurations, the computing device 100 may bea mobile device, such as a JAVA-enabled cellular telephone or personaldigital assistant (PDA), such as the i55sr, i58sr, i85s, i88s, i90c,i95c1, or the im1100, all of which are manufactured by Motorola Corp. ofSchaumburg, Ill., the 6035 or the 7135, manufactured by Kyocera ofKyoto, Japan, or the i300 or i330, manufactured by Samsung ElectronicsCo., Ltd., of Seoul, Korea. In some examples, the computing device 100is a mobile device manufactured by Nokia of Finland, or by Sony EricssonMobile Communications AB of Lund, Sweden.

In some examples, the computing device 100 may be a Blackberry handheldor smart phone, such as the devices manufactured by Research In MotionLimited, including the Blackberry 7100 series, 8700 series, 7700 series,7200 series, the Blackberry 7520, or the Blackberry Pearl 8100. In yetother examples, the computing device 100 is a smart phone, Pocket PC,Pocket PC Phone, or other handheld mobile device supporting MicrosoftWindows Mobile Software. Moreover, the computing device 100 may be anyworkstation, desktop computer, laptop or notebook computer, server,handheld computer, mobile telephone, any other computer, or other formof computing or telecommunications device that is capable ofcommunication and that has sufficient processor power and memorycapacity to perform the operations described herein.

Additionally or alternatively, the computing device 100 may be a digitalaudio player. For example, the computing device 100 is a digital audioplayer such as the Apple IPOD, IPOD Touch, IPOD NANO, and IPOD SHUFFLElines of devices, manufactured by Apple Computer of Cupertino, Calif. Inanother of these examples, the digital audio player may function as botha portable media player and as a mass storage device. In other examples,the computing device 100 is a digital audio player such as theDigitalAudioPlayer Select MP3 players, manufactured by SamsungElectronics America, of Ridgefield Park, N.J., or the Motorola m500 orm25 Digital Audio Players, manufactured by Motorola Inc. of Schaumburg,Ill. In still other examples, the computing device 100 is a portablemedia player, such as the Zen Vision W, the Zen Vision series, the ZenPortable Media Center devices, or the Digital MP3 line of MP3 players,manufactured by Creative Technologies Ltd. In yet other examples, thecomputing device 100 is a portable media player or digital audio playersupporting file formats including, but not limited to, MP3, WAV,M4A/AAC, WMA Protected AAC, AIFF, Audible audiobook, Apple Losslessaudio file formats and .mov, .m4v, and .mp4 MPEG-4 (H.264/MPEG-4 AVC)video file formats.

The computing device 100 may, alternatively or additionally, include acombination of devices, such as a mobile phone combined with a digitalaudio player or portable media player. In one of these examples, thecomputing device 100 is a Motorola RAZR or Motorola ROKR line ofcombination digital audio players and mobile phones. In another of theseexamples, the computing device 100 is an iPhone smartphone, manufacturedby Apple Computer of Cupertino, Calif.

Application Display Management

Referring now to FIG. 2A, the block diagram illustrates an examplesystem for displaying a plurality of resources on one or more displaydevices. The system includes a mobile computing device 102 that maycommunicate with one or more external display devices 202 a-n. Theexample in FIG. 2A shows a mobile computing device 102 with a nativedisplay 201, although devices without native displays may also be used.The mobile computing device 102 executes a plurality of resources 204a-n (collectively, 204). The window management system 206 and virtualgraphics driver 208 manage the locations and sizes of the display ofoutput data associated with each of the plurality of resources in auser-configurable display layout. In many examples, the mobile computingdevice 102 transmits the output data associated with each of theplurality of resources 204 to an external display device 202. In some ofthese examples, the mobile computing device 102 transmits the outputdata upon establishing a connection with the external display device202. Alternatively or additionally, the mobile computing device 102transmits the output data associated with each of the plurality ofresources 204 to the device's native display 201. For example, themobile computing device 102 might only transmit the output data to thedevice's native display or only transmit the output data to one or moreof the external display devices 202 a-n. In some examples, the mobilecomputing device 102 transmits the output data associated with certainof the plurality of resources 204 to the native display 201 andtransmits the output data associated with other ones of the plurality ofresources 204 to the external display devices 202 a-n.

Mobile computing device 102 may be configured to execute a plurality ofresources 204. In one example, the mobile computing device 102 is aclient 102 as described above in connection with FIGS. 1A-1C. In anotherexample, the mobile computing device 102 displays the output dataassociated with a resource 204 a in a plurality of resources 204 a-nexecuted by the mobile computing device 102. In some examples, themobile computing device 102 displays the output data associated witheach of the plurality of resources 204.

A resource in the plurality of resources 204 may include, withoutlimitation, a data file, an executable file, configuration files, anapplication, a desktop environment (which may itself include a pluralityof applications for execution by the user), a computing environmentimage (such as a virtual machine image), and/or operating systemsoftware or other applications needed to execute a computing environmentimage.

According to one or more arrangements, mobile computing device 102includes a window management service 206 allowing an external displaydevice 202 to display the output data associated with each of aplurality of resources 204 executed on the mobile computing device 102.The window management service 206 may also allow multiple resourcesrunning on the mobile computing device 102 to be viewed on an externaldisplay device 202 or the native display 201 at substantially the sametime, as opposed to allowing the output of one resource 204 to be viewedexclusively on the native display 201 or external display device 202. Inone example, the window management service 206, in conjunction with avirtual graphics driver 208, manages the display layout of the windowsdisplayed on the external display device 202 and the native display 201.In some examples, the virtual graphics driver 208 is a driver-levelcomponent that manages a virtual screen frame buffer storing output datathat will be displayed by the native display 201 on the mobile computingdevice 102 or an external display device 202. The window managementservice 206, in conjunction with the virtual graphics driver 208, mayfurther manage the boundaries and size of a screen space used to displayoutput data and on which display device the output data is displayed.

In some examples, an external display device 202 receives output dataassociated with each of the plurality of resources 204 and displays theoutput data in a user-configurable display layout. In one example, theexternal display device 202 includes a dock to which the mobilecomputing device 102 connects. In another example, the external displaydevice 202 includes a receiver for communicating with the mobilecomputing device 102 wirelessly, for example, via BLUETOOTH, Wi-Fi orother networking protocols, as described above in connection with FIGS.1A-1C. In still another example, the external display device 202 may bea display device 124 as described above in connection with FIGS. 1B and1C.

Referring now to FIG. 2B, the block diagram illustrates an examplesystem for mapping the display of one or more resources 204 of themobile computing device 102 on one or more display devices 201 and/or202. In various examples, the window management service 206 manages avirtual screen space 210. The virtual screen space 210 may map to thenative display 201 and one or more external display devices 202. Thewindow management service 206 may position output data associated withthe user interfaces of one or more resources 204 on the virtual screenspace 210 to specify where each user interface will be displayed. Insome examples, the window management service 206 positions the outputdata according to a user preference. In additional examples, the windowmanagement service 206 positions the output data according to a policy.In various examples, the window management service 206 positions theoutput data based on the resource 204 associated with the output data.

The window management service 206 communicates with the virtual graphicsdriver 208 to transmit output data associated with user interfaces ofresources 204 to the native display 201 and one or more external displaydevices 202. In some examples, the window management service 206 maytransmit output data and associated coordinates from the virtual screenspace 210 to the virtual graphics driver 208. In various examples, thevirtual graphics driver 208 stores the output data in a virtual screenframe buffer. In many examples, the virtual graphics driver 208transmits the entries in the virtual screen frame buffer to the nativedisplay 201 and external display devices 202. In many examples, thevirtual graphics driver 208 transmits an entry in the virtual screenframe buffer to a native display 201 or an external display device 202based on the position of the entry in the frame buffer.

Referring now to FIG. 2C, the user interface illustrates an exampleuser-configurable display layout in which the external display device202 displays the output data of the resources 204. In this example, theoutput data of the resources 204 is displayed in a grid display layout.The grid display layout may include one or more cells in an arrangement.A cell may display output data associated with a resource. In someexamples, more than one cell displays output data associated with thesame resource.

Additionally, in some examples, the cells are uniformly sized, whereasin other examples, the cells have different sizes. The cells may bearranged in any configuration. In some examples, the cells may bearranged in rows, columns, or both. A cell may have a descriptorassociated with the cell's position in the grid. The descriptor mayindicate the position of a cell within a row. In the example depicted inFIG. 2C, the cell for resource 204 a may have the descriptor “1-1,” thecell for resource 204 b may have the descriptor “1-2,” the cell forresource 204 c may have the descriptor “1-3,” the cell for resource 204d may have the descriptor “2-1,” and the cell for resource 204 d mayhave the descriptor “2-2.” In other examples, the cells may be numbered,e.g., “Cell 1,” “Cell 2,” etc. However, any system of choosingdescriptors known to those of ordinary skill in the art may be used.

In various examples, the window management service 206 configures a griddisplay layout according to the resources 204 being displayed on thenative display 201 or the external display device 202. In some examples,the service 206 configures a grid display layout according to the numberof resources 204 being displayed. In other examples, the service 206configures a grid display layout according to the size or amount ofcontent in the user interfaces of the resources 204. For example, if anexternal display device 202 will display four resources with comparableamounts of content, the window management service 206 may configure agrid display layout with four uniform cells. In another example, if anexternal display device 202 will display four resources and one resourceincludes three times as much content as the others, the windowmanagement service 206 may configure a grid display layout with threeuniform cells in a first row and a single cell in a second row. Thesingle cell in the second row may be three times as wide as the cells inthe first row. In various examples, the window management service 206may configure a grid display layout to reserve a cell for displayinginformation about the resources being displayed, such as a menu of theresources. In many examples, the window management service 206 mayconfigure a grid display layout to reserve a cell for allowing a user toconfigure the grid display layout.

Referring now to FIG. 2D, a user interface illustrates an exampleuser-configurable display layout providing a dynamic display layout inwhich the external display device 202 displays the output dataassociated with the plurality of resources 204. In this example, windowson the external display device 202 that display output data forresources 204 may be dynamically positioned and sized. The windowmanagement service 206 may position a user interface for a resource at adefault position and with a default size chosen according to a policy,the resource 204, or any other method. The window management service 206may order overlapping user interfaces such that higher-order userinterfaces obscure lower-order user interfaces. The window managementservice 206 may transmit output data to the virtual graphics driver 208reflecting the obfuscation. The user may re-position or re-size a windowby, for example, clicking and dragging the window or a window edge. Inthese examples, the virtual graphics driver 208 may detect the user'schange to the window, and transmit information about the user's changeto the window management service 206. The window management service 206may process the change and transmit updated output data to the virtualgraphics driver 208. In some examples, the user moves the user interfacefor a resource 204 to any location on a native display 201 or externaldisplay device 202. In some examples, the user moves the user interfacefor a resource 204 to a different display device. In some examples, theupdated output data indicates that one user interface's size has beenincreased or location has been adjusted to obscure another userinterface. In other examples, the updated output data indicates that oneuser interface's size has been decreased or location has been adjustedsuch that more of another user interface shall be visible.

Referring now to FIG. 3A, a block diagram illustrates example virtualscreen spaces 210 provided by a mobile computing device attached to oneor more external display devices. As shown in FIG. 3A, the mobilecomputing device 102 includes a virtual graphics driver 208 and avirtual screen 210. The virtual screen 210 includes a plurality ofvirtual screen spaces 310 and 312 a-n. Virtual screen space 310 may be anative display screen space for the native display 201 on the mobilecomputing device 102. The other virtual screen spaces 312 a-n may beextended screen spaces that correspond to the displays of externaldisplay devices 202. The window management service 206 and virtualgraphics driver 208 manage the virtual screen 210. In one example, thevirtual graphics driver 208 uses a virtual screen frame buffer to managethe mobile computing device's native display 201 and change the nativedisplay's 201 screen resolution. In another example, the virtualgraphics driver 208 uses a virtual screen frame buffer to manage anextended screen space 312 and to change a resolution of the extendedscreen 312.

In some examples, the virtual graphics driver 208 allocates and managesa plurality of virtual screen spaces 310, 312 a-n and virtual screenframe buffers. In some of these examples, each virtual screen space andvirtual screen frame buffer has a resolution independent of the otherscreen spaces and frame buffers. In one of these examples, output dataassociated with each of the plurality of resources 204 may reside withinany of the virtual screen spaces 310, 312 a-n. In another of theseexamples, each of the extended screen spaces 312 a-n is associated withat least one external display device 202, depending on the capabilitiesof the device.

In various examples, the window management service 206 and the virtualgraphics driver 208 allocate and manage the display, on a plurality ofexternal display devices 202, of output data associated with a pluralityof resources. For example, output data associated with a resource 204 adisplays on a mobile computing device 102, output data associated with aresource 204 b displays on one external display device 202 a, and outputdata associated with a resource 204 c display on another externaldisplay device 202 b. In another of these examples, the windowmanagement device 206 identifies one of the external display devices 202for displaying output data generated by a resource 204 a based upon atype of the resource 204 a. For example, the window management service206 may determine that a type of resource rendering a video may displayon a television screen, while a type of resource rendering a wordprocessing application may render on a display of a laptop computer.

Referring now to FIG. 3B, a block diagram illustrates an example mobilecomputing device 102 providing a virtual screen 210 with virtual screenspaces 310, 312 a-n of varying resolutions. In this example, the virtualscreen 210 includes a native display screen space 310 corresponding tothe native display 201 of the mobile computing device 102 with aresolution of 320 pixels×240 pixels. The virtual screen 210 alsoincludes an extended screen 312 a corresponding to the display of anexternal display device 202 with a resolution of 1024 pixels×768 pixels,an extended screen 312 n-1 corresponding to the display of an externaldisplay device 202 with a resolution of 800 pixels×600 pixels, and anextended screen 312 n corresponding to the display of an externaldisplay device 202 with a resolution of 640 pixels×480 pixels. In manyexamples, the virtual screen 210 may include a native display screenspace 310 and any number of extended screens 312 of any resolution. Theentire virtual screen space 210 may be mapped into a single virtualscreen frame buffer, although examples that map into multiple buffersmay be used.

Referring now to FIG. 3C, the block diagram illustrates an examplelogical representation of a plurality of virtual screen spaces managedby a virtual graphics driver. In this example, the virtual graphicsdriver 208 manages multiple virtual screen spaces with differentresolutions in a virtual screen frame buffer. In this example, thenative display 201 of the mobile computing device is the primary displayand the external display device 202, corresponding to the extendedscreen 312 a, is a secondary display. In various examples, output dataassociated with resources 204 on the native display screen space 310will be displayed on the native display 201 and output data associatedwith resources 204 on the extended screen space 312 a will be displayedon the external display device 202 associated with the extended screenspaces 312 a. In other examples, all output data associated withresources 204 may be displayed on the native display 201. In still otherarrangements, all output data associated with resources 204 may bedisplayed on an external display device such as external display device202.

Providing a Native User Experience for Remoted Applications

FIG. 5 illustrates an example system in which applications may beremotely executed at a server while providing display and userinteraction through a client device such as mobile device 102.Accordingly, a user may view and interact with an application remotedfrom (e.g., remotely executed by the server (e.g., remote computer 501))at a client device (e.g., mobile device 102) without requiring theapplication and/or data to be installed or stored on the client device.The system of FIG. 5 may include a mobile computing device 102 (e.g.,similar to that shown in FIG. 2B) configured to execute and/or store oneor more resources 204 such as applications executing on the mobilecomputing device 102. In some examples, at least one resource may be anoperating system executing on the mobile device 102 and one or moreother resources may execute within the context of the operating system.The mobile device 102 may further execute a windows management service206 that may communicate with other applications executing on the mobiledevice 102 and, in some examples, may communicate with a virtualgraphics driver 208 and the resources or applications 204 executing onthe mobile device 102. The mobile computing device 102 may furtherexecute a virtual graphics driver 208, and may store a buffer forgenerating a virtual screen space 210 that may include a buffer for anative display screen space 210 a. The mobile device 102 may communicatewith a native display 201 of the mobile device 102 on which applicationoutput generated by a resource 204 may be displayed. The mobile device102 may further communicate with a remote computer 501 that may executeone or more resources 505A-505N (generally referred to as remoteresources 505) which may in some examples be remote applications 505.The remote computer 501 may further execute a remoting client 510. Theremote applications 505 may be executed by the remote computer for useat the mobile device 102 in one or more arrangements as discussed infurther detail below. When one or more remote applications 505 areexecuted by the remote computer for use at the mobile device 102, thoseapplications may be considered remoted applications.

According to one or more arrangements, resources 204 executing on themobile device 102 and/or resources 505A-505N may be applicationsconfigured to accept data inputted by a touch screen. For example, theapplications may be modified versions of applications that typically donot receive data from a touch screen. These modified applications 204may receive data inputted by a user via a touch screen of the mobiledevice 102, and may be modified to accommodate typical touch screeninput functions like a virtual keyboard and a virtual scroll menu. Forexample, a modified version of SAFARI, a web browser published by APPLE,may be modified to pan up when a user selects or gives focus to an editcontrol such as a text box. SAFARI pans the application upwards toaccommodate the virtual keyboard displayed over the browser and so thata user may view the text box while typing on the virtual keyboard.

Touch input may include a variety of hand or finger movements andactions including touching a point on the screen, swiping movements,flicking movements, multi-finger or multi-touch actions (e.g., pinching,expansion) and gestures and the like. The touch input may triggerdifferent functionalities depending on the type of application receivingthe input. For example, some applications may receive a flicking actionas closing the application while other application may interpret aflicking input as moving the application window in a certain direction.Each applications may define its own interpretation of different typesof touch input or may use a standard definition provided by anunderlying operating system.

According to one or more configurations, the mobile device 102 maycommunicate with remote computer 501 in a variety of ways. The remotecomputer 501 may be a server, a client or any other computing machine.In some examples the remote computer 501 may be a remote applicationserver that executes one or more applications for mobile device 102.Accordingly, in some examples, the mobile device 102 may communicatewith the remote computer 501 over one or more virtual channels. In someexamples, virtual channels may be established over a network and may bereferred to as a control virtual channel. In other examples, the virtualchannel may be a seamless virtual channel. A control virtual channel maybe used to remote control commands and other miscellaneous commands(e.g., for an application) while the seamless virtual channel may beused to remote application windows, a taskbar, a systray, etc. Thus, insome examples, each virtual channel may remote different functions andcontent. In still other examples, the virtual channel may be establishedby a window management service 206 executing on the mobile device 102,or the virtual channel may be established by both the window managementservice 206 and a remoting client 510 executing on remote computer 501.The virtual channel may in some examples facilitate communication sentusing the ICA protocol.

In some examples, the remote computer 501 may execute a remoting client510. The remoting client 510 may be a control virtual channel or aseamless virtual channel and may be a remoting application thatcorresponds to the virtual channel used by the client 510 to transmitdata to and receive data from the mobile device 102. In some examples,the remoting client 510 may collaborate with the window managementservice 206 (of the mobile computing device 102) to modify remoteapplications 505 for remote display on the mobile device 102. The windowmanagement service 206 may be, for example, a CITRIX RECEIVER publishedby CITRIX SYSTEMS. In some examples, the remoting client 510 maycommunicate with the remote applications 505 to intercept eventproviding notifications and data generated by the remote applications505. In particular, the remoting client 510 may perform event-baseddetection of one or more controls using application programminginterfaces provided by one or more of the remote applications 505. Forexample, at least one remote application 505 may be an operating systemexecuting on the remote computer 501. Another remote application 505Bmay be executing on the remote computer 501 and within the context ofthe operating system 505. In these examples, the remoting client 510 mayintercept events generated by controls within the remote application505B using application program interfaces made available by theoperating system 505. The controls may be selected by the remotingclient 510 based on whether the control has focus or is on apredetermined list of controls of interest. A control, in some examples,may be an object within an application that a user interacts with, e.g.,a text box, drop down menu, radio button, button, check box, edit box,combo box etc. The control may further be referred to as a field orinteractive element. In some examples, the remoting client 510 mayintercept the control-generated events by registering with acommunication interface associated with the application 505B to receivenotifications when a focus-change event occurs within the application505B. For example, the remoting client 510 may receive a notificationwhen an object or control receives focus, e.g., indicating that a userselected a text box within the application.

In some examples, the remoting client 510 may communicate with thewindow management service 206 over the virtual channel. In a particularexample, the remoting client 510 may send intercepted eventnotifications over the virtual channel to the window management service206. In other examples, the remoting client 510 may transmit locationcoordinates for a control, the type of control, the contents of acontrol, the window handle of a control, and/or parent windowinformation for a control. Window handles or other identificationinformation for elements within an interface or application may includea globally unique identifier (GUID). The window management service 206may receive information from the remoting client 510 and adjust ormodify display of an application 204 on the native display 201 using thereceived information. Adjusting the display may include panning, zooming(in or out), scrolling or otherwise modifying the display of theapplication 204.

In some examples, the remote computer 501 may execute one or moreresources 505. These resources, in some examples, may be applications.In other examples, at least one resource may be an operating systemexecuting on the remote computer 501. In those examples, the otherapplications 505 may execute within the context of the operating system.In some instances, the applications 505 may correspond to remoteapplications 505 from the perspective of device 102 and one or more ofapplications 505 may be remoted to mobile device 102 for use by the userat mobile device 102.

FIG. 6 illustrates a general method 600 for altering or modifying thedisplay of a remoted application on a mobile device. For example, instep 602, an application executing on a computer remote from the mobiledevice may intercept a focus event notification generated in response toa control within a remoted application receiving focus. The remotecomputer may forward the received or intercepted focus eventnotification to a client device through which a user is viewing andinteracting with the remoted application (e.g., mobile computing device102 of FIG. 5) in step 605. Upon receiving the focus event notification,an application executing on the mobile computing device may modify adisplay of the remoted application in response to receiving thenotification and according to information associated with the event(Step 610).

FIG. 7 is a flowchart illustrating a method that may be performed by acomputer executing an application for a remote client device (e.g.,within the general process of method 600). In step 700, for example, aremoting management application executing on the computer may interceptor otherwise receive a focus event notification. The remoting managementapplication may, in some examples, be a remoting client 510 executing ona remote computer 501. In other examples, the application may be anyapplication executing on a remote computer 501 and able to hook intofunction calls issued by an application executing on the remote computer501. The remoting management application executing on the remotecomputer 501, in a particular example, may be a component insideWFSHELL.EXE (ICACTLS.DLL) or another service of Citrix XenApp orXenDesktop server. In other examples, the remoting managementapplication may be an application managing a control or seamless virtualchannel established between the remote computer 501 and the mobiledevice 102. The focus event notification may be a call issued by aremote application executing on the remote computer 501 when a controlor field within the remote application receives focus, e.g., a userselects or otherwise highlights the control or field through mobiledevice 102. In some examples, the control may be any object or controlor user interactive or input element, such as: an edit box, a textbox, amemo field, a combo box, a drop-down menu, a slider, a list box, or anyother similar object or control. The function may, for example, be afunction such as ‘focus combo box” or any other function that generatesa notification indicating a control receiving focus. In some examples,the remoting management application may use event-based detectionfacilitated by WINDOWS 7 UI AUTOMATION application program interfaces.In other examples, the remoting management application may useevent-based detection facilitated by any API. In these examples, theapplication may register for notifications provided by these APIs usinga COM interface associated with a particular control and/or a particularfunction.

The remoting management application may send additional information tothe mobile device 102, e.g., separately or as part of the notificationmessage, including: the type of control or interface element thatreceived focus (e.g., combo box, textbox); the name or an identifier ofthe control that received focus; the location or coordinates of thecontrol within the application (e.g., where in the application outputthe control is located); the content of the control (e.g., valuesassigned to the control, strings associated with the control, etc.); awindow handle of the control; a window identifier of the windowdisplaying the control; the location or coordinates of the parent windowdisplaying the control; or any additional information that could be usedto determine the location of the control within the application outputdisplayed by the mobile device 102.

In step 705, the remote computer 501 may determine the type of object orcontrol element receiving focus and/or a position thereof. For example,the computer may determine whether the control element is a text entryfield, a menu of selectable values, a radio button or the like. Thecomputer may also determine position information based on position dataspecified in the notification message, including the coordinates andsize of the control element on which focus is placed. In step 710, theremote computer 501 may then determine a general type of user controlelement to activate on the mobile device based on the determined type ofcontrol element of the remoted application receiving focus. For example,if the control element of the remoted application corresponds to a textentry field, the computer may determine that a software keyboard of typestandard alphanumeric would be appropriate for interacting with the textentry field in a touch-input environment. In another example, if thecontrol element of the remoted application corresponds to a number entryfield (e.g., only numbers are permitted in the field), the computer maydetermine that a software keyboard of a number pad type may be mostappropriate for interacting with the number entry field.

In step 715, the computer may transmit a command to the mobile device toactivate a native control element corresponding to the determined typeof control element locally on the mobile device. The command may betransmitted through a virtual channel between the remoting applicationand a remoting client application executing on the mobile device.Additionally, in one or more examples, if the type of control element tobe shown or activated on the client device is a software keyboard, thecomputer may transmit the command identifying the type of the controlelement and identification of an editable area or field for which thecontrol element is to be activated. The identification of the editablearea or field may include coordinates, size information and the like. Inanother example, if the type of control element to be shown or activatedlocally on the client device is a picker control (e.g., a menu or scrollselection bar), the computer may transmit the command along with anidentifier of the picker control, an area or field definition (e.g.,coordinates, size information), contents of the picker control (e.g.,the selectable items), current selection index, a title of the pickercontrol and/or window and parent window handles.

In some arrangements, the remote computer 501 might not determine amobile device-native control element or type thereof to activate or use.Instead, the user of the mobile device may manually select or activate anative control element at the mobile device.

In step 720 the remote computer may receive an indication (e.g., anotification or confirmation) from the mobile device of the activationof a user control or input element native to the mobile device. Theindication may include, for example, a confirmation of the state of thecontrol element (e.g., show/hide), success or failure from execution ofthe command and/or an identifier of the local control element, e.g.,mirroring the control identifier from the original command from theremote computer.

In some arrangements, the remote computer 501 may receive a returnoperation status message from the client device (e.g., mobile device102) in step 725, indicating an operation status of an activated localcontrol element such as a picker control. For example, the returnoperation status message may include the identifier of the control, theoperation status of the control and a selection index if the operationstatus indicates a selection made by the user. The selection index mayidentify the selected item. The operation status may include success(indicating that a selection has been made by the user) or cancel/abort(e.g., if the user has deactivated the control element withoutselection).

Additionally or alternatively, in step 730, the remote computer 501 mayfurther update the application display to reflect a selection made by auser (e.g., in a picker control element) in response to a notificationfrom the client of the operation status and the selection. For example,the selection field may be updated with the selected value and theupdated application display may be transmitted to the client device(e.g., mobile device 102) for display. The application display updatemay then be transmitted to the client device in step 735.

In step 740, the remote computer 501 may receive another notificationindicating that focus has left the control element and/or the remotedapplication. In response, the remote computer 501 may issue aninstruction to the mobile device 102 (or a client application executingthereon) to return the application display to an original state and/orto deactivate the native control element in step 745 (e.g., if theapplication display was previously modified upon the remoted applicationreceiving focus). In some arrangements, the remote computer 501 mayissue the instruction only upon receiving notification that the nativecontrol element is no longer active (e.g., being displayed) or in use.

FIG. 8 is a flowchart illustrating a process by which a device such asmobile device 102 (FIG. 5) may receive output data and instructions froma remote computing device executing a remoted application. In step 800,the device (e.g., a client device) may execute a management applicationto provide interactivity with and receive data output from anapplication remotely executing on a server or other remote computingdevice. For example, the management application executing on the mobiledevice 102 may modify the display of the remoted application on themobile device 102 in response to receiving instructions from the remotecomputing device (e.g., as described with respect to FIG. 7). In someexamples, the management application may be a window management service206 executing on the mobile device 102. In other examples, themanagement application may be any application able to receive event andcontrol information from a remote computer 501 and use it to modifyoutput displayed on the native display 201 of mobile device 102. In step805, the device may receive, from the remote computer executing theapplication, an instruction to activate a type of control element. Inone or more examples, the instruction may be received from the remotecomputer in response to the remote computer detecting an editable orcontrol field receiving focus (e.g., a user selecting, through theclient device, a text entry field in a remoted application display).

In response to the instruction, the device may determine a nativecontrol (e.g., user input) element to activate based on the type ofcontrol element specified in the instruction in step 810. For example,if the general type of control element corresponds to a standardalphanumeric keyboard, the device may identify a native control elementmatching the specified type such as an iOS standard alphanumerickeyboard (if it is an iOS mobile device), or an Android standardalphanumeric keyboard (if it is an Android mobile device). In somearrangements, the general types of controls supported by or available onthe client device may be reported to the remote computer executing theapplication so that the remote computer may select an appropriategeneral type. Alternatively or additionally, the remote computer mayprocess the focus event differently if a corresponding general type ofcontrol element is not supported by the client device, as is describedin further detail herein. In some examples, the instructions may specifyactivation of multiple types of controls. Operation of the multiplenative controls may be based on the use and specification of the GUIDassigned to each native control.

Upon determining an appropriate control element corresponding to thespecified type of control element, the device may activate or executethe determined native control in step 815. In one example, activationand/or execution of the native control may include modifying the nativedisplay interface to display the control. Activation and/or execution ofthe native control might also include extracting control element values(e.g., values within a drop-down menu) and incorporating those valuesinto the native control element (e.g., the virtual picker in the aboveexample). For example, in some arrangements, the remote computerexecuting the remoted application may transmit control values includedin the application control element receiving focus to the device fordisplay in the native control element. Accordingly, upon receiving theevent notification and control information, the window managementservice 206 at the mobile or client device may determine whether thecontrol is a type of control having associated values. Upon determiningthat the control has associated values, the window management service206 may modify the display of the application to include the receivedvalues. In one example, if one or more strings are associated with acombo box having received focus, the window management service 206 maymodify the display to display a combo box that includes those strings.In other aspects, a client executing on the device, or a windowmanagement service 206, may use local controls native to the device todisplay a remote control or to display graphics representative of aremote control. For example, when a remote Windows Combo Box ispresented in an application, the device may display and/or use a localiPad picker control. Thus, the remote application displayed on thedevice may adopt the appearance of a device native application and mayinclude at least some native functionality.

The device may further determine, in step 820, whether the nativecontrol element will (or does) obscure the element of the remotedapplication receiving focus. For example, the device may determine anamount of the remoted application element being obscured (e.g., apercentage, absolute amount in pixels, inches or other metric), aparticular area being obscured (e.g., obscuring a left part of a textentry field may be less important than obscuring a right part of thetext entry field for language environments that read left to right), andthe like. In some arrangements, the remoted application element mightnot be considered obscured if the amount obscured or portion obscureddoes not meet a predefined rule or threshold. For example, a remotedapplication element might only be considered obscured if at least 25%,at least 10%, at least 50%, etc. of the element is not visible. Inanother example, a remoted application might only be considered obscuredif any portion of the left side of a text entry field (e.g., any part ofthe left 50% of the text entry field) is hidden from view. Other rulesfor determining when a control element is obscured may be defined andused.

If the device determines that the application control element will be oris obscured by the native control element, the device may determine, instep 825, a manner in which to modify the local display such that atleast the application control element is no longer obscured. Forexample, if a mobile device native keyboard is to be displayed at thebottom of the mobile device display and will obscure the applicationcontrol element, the device may determine that the one or more portionsof the local display (desktop interface or application specificwindow(s) or portions thereof) should be panned upward (e.g.,auto-scroll). Additionally or alternatively, the device may modify thedisplay (entire desktop, portions of the desktop and/or specificwindows) to include a scrolling feature so that a remainder of theapplication display may be viewed once the display is panned upward ifthere is insufficient display real estate. In another example, thedevice may modify the application window to zoom out (e.g., shrink theapplication display) so that the application display fully fits withinthe mobile device display.

In step 830, the device may subsequently modify the display inaccordance with the determined manner to avoid obscuring theeditable/control field. Alternatively, if the editable/control fieldreceiving focus will not be obscured, the device might not modify thedisplay. In some examples, steps 820-830 may be performed in conjunctionwith (e.g., before, during or after) activation of the native controlelement in step 815.

In some examples, the device may transmit a confirmation message to theremote computing device confirming activation of the native controlelement as shown in step 835. Alternatively or additionally, the devicemay further transmit a return operation status message to the remotecomputing device in step 840, as described above with respect to steps725 and 730 of FIG. 7. For example, status messages may be provided whenthe device detects a user selection of an item in the picker control. Inanother example, the device may transmit a status message upon detectinga user cancelling or aborting the picker control. These events may bereported to the remote computing device in the update message forappropriate handling by the remote computing device. If the updatemessage includes an event that causes changes to the applicationdisplay, for instance, those changes to the application display may bereceived from the remote computing device for updating the localapplication display.

The client device may further receive, in step 845, a message indicatingthat focus has left the editable/control field and providinginstructions to deactivate the corresponding native control element. Inresponse, the client device may deactivate the native control elementand return the application display to a previous state (e.g., prior toactivation of the native control element) in step 850 if modificationwas performed.

The processes of FIGS. 7 and 8 may further include transmitting actionsperformed on or through a native control element of the client deviceback to the remote computing device and remote application. For example,Application A executing on the remote computing device may generateapplication output which may be displayed in an application outputwindow on the remote computing device. The application output generatedby Application A is subsequently transmitted to the client device whereit is displayed within an application output window thereon (e.g., alocal application window). In some examples, when an editable combo boxfield within the remotely generated application output receives focus, aclient or a window management service 206 may intercept the on-focusevent and may display or invoke a native, virtual picker control, e.g.,an iPad picker control. Within the local application window and amongstthe remotely generated application output, the native, virtual pickercontrol is displayed. A user may interact with the native control togenerate input. Once the control is used to generate input, the clientor window management service 206 may transmit the input to the remotecomputing device for processing within the context of the remotedapplication. For example, upon receiving the input, the remote computer501 may inject the control input into an actual control displayed withinthe actual application output generated by Application A. In aparticular example, injection of the received control input may beaccomplished using a Windows UI Automation API. Changes in the remotedapplication based on the received input may then be outputted back tothe client device. This process may repeat until the remoted applicationis closed and/or the remoting relationship between the client device andthe remote computing device is ended.

Additionally or alternatively, the remote computing device (executingthe remoted application) may further be configured to determine whetherthe client device supports or has local control elements such as anative virtual keyboard or a native picker corresponding to a particulartype or category of control element. For example, the client device'scapabilities may be specified to the remote computing device and assuch, the remote computing device may make the above noteddetermination. If the client device does not support or does not have alocal control element corresponding to a determined type of controlelement corresponding to the editable/control field, the remotecomputing device may generate a virtual keyboard or other controlelement as part of the remoted application or separately from theremoted application and output the display of the virtual keyboard tothe client device (similar to the remoting of the application). In oneparticular example, the virtual control element generated by the remotecomputing device may be executed and remoted as a separate application.In another example, the virtual control element may be included withinand as part of the existing remoted application receiving focus.

According to another aspect, the activation of a native control elementmay be switched on or off by the user or by a service providing theapplication remoting capability. Accordingly, if the user or the servicedoes not wish to use native controls, the device might not automaticallytrigger a native control element upon receiving a focus eventnotification for an editable field. Additionally or alternatively, theremote computing device executing the application may be configured todetermine whether an editable/control field will be obscured and todetermine and provide instructions for modifying a local display of theclient device in response. Accordingly, the remote computing device maytransmit instructions for modifying the local display and/or theapplication display of the client device.

FIGS. 9A and 9B illustrate example interfaces displaying the use ofnative controls including a virtual keyboard. In FIG. 9A, for example, anative control of the device 900 such as virtual keyboard 901 isactivated and displayed for entry of input into a text entry fieldwithout modifying a remoted application display 903. As a result, thetext entry field and other potentially important or relevant portions ofthe application display 903 become obscured by the virtual keyboard 901.

In FIG. 9B, to avoid obscuring the text entry field 905, the applicationdisplay may be panned upward. In some arrangements including thearrangement of FIG. 9B, the display of an entire desktop including theremoted application display 903 may be modified. Panning may includemoving the application display 903 in a particular direction (in thisexample, towards the top of the display) with or without modifying theproportions or orientation of the application display 903 or desktop. Insome examples, panning may result in elements that were previouslyvisible being moved off of the device display. For example, recycle binicon 907 in FIG. 9A is moved off of the displayable area after theapplication display 903 is panned upward as shown in FIG. 9B. The amountor degree to which the application display 903 is modified (e.g.,panned) may be determined based on various rules and thresholds. In aparticular example, the application display 903 may be panned until atleast 75% of the text entry field is visible. In another example, theapplication display 903 may be panned until an entirety of the textentry field is visible.

FIGS. 10A and 10B illustrate other example interfaces displaying the useof native controls including a scrolling picker. In FIG. 10A, a webbrowser application 1001 is displayed with content having variouscontrol elements including a drop down menu 1003. The drop down menu1003 may include multiple selectable values that, in some arrangements,may be difficult to see because of font size, the number of values, sizeof the drop down portion of the menu and the like.

Accordingly, in FIG. 10B, the interface may display a native pickercontrol element 1005. The native picker element 1005 may be populatedwith the values included in drop down menu 1003. The native pickercontrol element 1005 may be displayed for easier viewing andaccessibility (e.g., larger font size, easier selection mechanism,etc.). In the illustrated example of FIG. 10B, the application displaymight not be modified. Because the values listed in the drop down menu1003 are also displayed in native picker control element 1005, obscuringpart or all of the drop down menu 1003 might not have as significant animpact in usability. In some examples, the application display may bemodified to insure that the non-expanded drop down menu portion remainsvisible so that a user may confirm his or her selection once populatedinto the drop down menu 1003. In yet other examples, the applicationdisplay may zoom in to the drop down menu 1003 or a portion thereof toincrease viewability.

The methods and features recited herein may further be implementedthrough any number of computer readable media that are able to storecomputer readable instructions. Examples of computer readable media thatmay be used include RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, DVD or other optical disk storage, magneticcassettes, magnetic tape, magnetic storage and the like.

Moreover, while many of the aspects and features described hereininclude the use of a mobile device, stationary or fixed location devicesmay also include the same or similar aspects and features. For example,a personal computer or workstation (e.g., plugged into a wall socket)may include touch input controls and provide access to a remotedapplication from a remote computing device. Accordingly, similar nativecontrol elements may be generated and used from the personal computer orworkstation in similar fashion to a mobile device such as a tabletcomputer.

Additionally or alternatively, in at least some examples, the methodsand features recited herein may be implemented through one or moreintegrated circuits (IC s). An integrated circuit may, for example, be amicroprocessor that accesses programming instructions or other datastored in a read only memory (ROM). In some such examples, the ROMstores programming instructions that cause the IC to perform operationsaccording to one or more of the methods described herein. In at leastsome other examples, one or more of the methods described herein arehardwired into an IC. In other words, the IC is in such cases anapplication specific integrated circuit (ASIC) having gates and otherlogic dedicated to the calculations and other operations describedherein. In still other examples, the IC may perform some operationsbased on execution of programming instructions read from ROM or RAM,with other operations hardwired into gates and other logic of IC.Further, the IC may output image data to a display buffer.

Although specific examples of carrying out various features have beendescribed, those skilled in the art will appreciate that there arenumerous variations and permutations of the above-described systems andmethods that are contained within the spirit and scope of the disclosureas set forth in the appended claims. Additionally, numerous otherexamples, modifications and variations within the scope and spirit ofthe appended claims will occur to persons of ordinary skill in the artfrom a review of this disclosure.

What is claimed is:
 1. A method comprising: receiving, by a clientdevice, from a remote computing device, a control value for anapplication control element of an application executing on a remotecomputing device; activating, by the client device, a native graphicaluser input element native to the client device; and populating, by theclient device, the native graphical user input element with the controlvalue received from the remote computing device.
 2. The method of claim1, comprising: receiving, by the client device, from the remotecomputing device, an instruction specifying a type of the applicationcontrol element, wherein a type of the native graphical user inputelement corresponds to the type of the application control element. 3.The method of claim 1, comprising: modifying the application controlelement of the application executing on the remote computing devicebased on at least one characteristic of the native graphical user inputelement native to the client device.
 4. The method of claim 1,comprising: generating, by the client device, a display simultaneouslycomprising the native graphical user input element native to the clientdevice and the application control element of the application executingon the remote computing device.
 5. The method of claim 4, comprising:determining, based on one or more of a size and a position of the nativegraphical user input element, whether a display of the native graphicaluser input element will overlap a display of the application executingon the remote computing device when the native graphical user inputelement is activated; and adjusting the display of the application sothat at least a portion of the display of the application is notoverlapped by the display of the native graphical user input element. 6.The method of claim 5, wherein the portion of the display of theapplication that is not overlapped by the display of the nativegraphical user input element comprises the application control element.7. The method of claim 1, comprising: receiving, by the client device,an interaction with the native graphical user input element; andtransmitting, by the client device, the interaction to the remotecomputing device.
 8. The method of claim 7, wherein the native graphicaluser input element comprises a menu with an item corresponding to thecontrol value, wherein the interaction comprises a selection of theitem, and wherein the transmitting the interaction comprises anidentification of the item.
 9. The method of claim 1, wherein the nativegraphical user input element comprises a virtual picker, and wherein thevirtual picker comprises the control value received from the remotecomputing device.
 10. A method comprising: transmitting, by a firstcomputing device, to a second computing device, a display of a remotedapplication executing on the first computing device; receiving, by thefirst computing device, input causing an application control element ofthe remoted application to receive focus; and transmitting, by the firstcomputing device, to the second computing device, a control value of theapplication control element, the transmitted control value being forpopulating a native graphical user input element native to the secondcomputing device.
 11. The method of claim 10, comprising: transmitting,by the first computing device, to the second computing device, a requestfor the second computing device to activate, separately from the displayof the remoted application, the native graphical user input elementnative to the second computing device.
 12. The method of claim 10,comprising: determining a type of the application control element of theremoted application, wherein the type of the native graphical user inputelement native to the second computing device corresponds to the type ofthe application control element of the remoted application.
 13. Themethod of claim 10, comprising: receiving information regarding acharacteristic of the native graphical user input element native to thesecond computing device; and modifying the application control elementof the remoted application executing on the first computing device basedon the characteristic of the native graphical user input element nativeto the second computing device.
 14. The method of claim 10, comprising:transmitting, by the first computing device, to the second computingdevice, a request for the second computing device to generate a displaysimultaneously comprising the native graphical user input element nativeto the second computing device and the application control element ofthe remoted application executing on the first computing device.
 15. Themethod of claim 10, comprising receiving different input causing theapplication control element of the remoted application to lose focus;and in response to receiving the different input, transmitting a requestfor the second computing device to deactivate the native graphical userinput element native to the second computing device.
 16. The method ofclaim 10, comprising: transmitting, by the first computing device, tothe second computing device, at least one of a size and a position ofthe application control element of the remoted application.
 17. Asystem, comprising: a computing device, comprising: a first processor;and a first memory storing first computer-readable instructions that,when executed by the first processor, cause the computing device to:transmit, to a client device, a display of a remoted applicationexecuting on the computing device; receive input causing an applicationcontrol element of the remoted application to receive focus; andtransmit, to the client device, a control value of the applicationcontrol element of the remoted application; and the client device,comprising: a second processor; and a second memory storing secondcomputer-readable instructions that, when executed by the secondprocessor, cause the client device to: receive the display of theremoted application executing on the computing device; receive thecontrol value of the application control element of the remotedapplication executing on the computing device; activate a nativegraphical user input element native to the client device; and populatethe native graphical user input element with the control value receivedfrom the computing device.
 18. The system of claim 17, wherein the firstcomputer-readable instructions, when executed by the first processor,further cause the computing device to: transmit, to the client device, arequest for the client device to activate, separately from the displayof the remoted application, the native graphical user input elementnative to the client device; and wherein the second computer-readableinstructions, when executed by the second processor, further cause theclient device to: receive the request to activate, separately from thedisplay of the remoted application, the native graphical user inputelement native to the client device; and activate, separately from thedisplay of the remoted application, the native graphical user inputelement native to the client device.
 19. The system of claim 17, whereinthe second computer-readable instructions, when executed by the secondprocessor, further cause the client device to: generate a displaysimultaneously comprising the native graphical user input element nativeto the client device and the application control element of the remotedapplication executing on the computing device.
 20. The system of claim17, wherein the first computer-readable instructions, when executed bythe first processor, further cause the computing device to: send, to theclient device, information regarding a type of the application controlelement; and wherein the second computer-readable instructions, whenexecuted by the second processor, further cause the client device to:receive, from the computing device, the information regarding the typeof the application control element, wherein a type of the nativegraphical user input element corresponds to the type of the applicationcontrol element.